On mips, 1**np.nan and np.nan**0 may be NaN not 1
authorDebian Science Team <debian-science-maintainers@lists.alioth.debian.org>
Sat, 21 Sep 2024 16:21:40 +0000 (17:21 +0100)
committerRebecca N. Palmer <rebecca_palmer@zoho.com>
Sat, 21 Sep 2024 16:21:40 +0000 (17:21 +0100)
commit8637b7c6cd5e7218cd9ba95d8848b7548652c2f7
treed962bc5560cd312d0d9fedc69534fd29dc6993f7
parente46b48cc73337c93db246e4c65bf8204fd484260
On mips, 1**np.nan and np.nan**0 may be NaN not 1

Done this way not a plain xfail to allow only this difference,
not clearly wrong answers

(The same hardware's "invalid value encountered" warnings,
probably from sNaN/qNaN being reversed, are ignored elsewhere:
d/rules and xfail_tests_nonintel_io.patch)

https://en.wikipedia.org/wiki/NaN#Encoding

Author: Rebecca N. Palmer <rebecca_palmer@zoho.com>
Forwarded: no

Gbp-Pq: Name mips_pow_nan.patch
pandas/tests/arrays/floating/test_arithmetic.py
pandas/tests/arrays/sparse/test_arithmetics.py